VB Code Flush - Version 1.1 Copyright (C) 1992 by Lou A. Moccia For use with Microsoft Visual Basic 1.0. In Visual Basic, if you load a project, then edit code, Make EXE File, edit code, Make EXE File, and so on, your EXE file will increase in size each time. If you do this for a long period of time, your EXE file will be substantially larger than if you simply loaded the project and made the EXE file right away. A tip was discovered that says in order to create the smallest possible EXE file, you have to Save Text and Load Text (replacing the existing code) for all of the forms and modules in a project, then exit and restart Visual Basic, reload the project, and immediately make the EXE file. However, even with small projects this can be an dreadful chore. VB Code Flush takes care of the tedious part of this process for you. Simply load a project in Visual Basic and then run VB Code Flush, and it will perform the Save Text and Load Text commands for every form and module in the project. Once done, all you have to do is Save Project, exit and restart Visual Basic, reload the project, and Make EXE File. VB Code Flush requires VBRUN100.DLL. I won't bother explaining how to set up the application, because it is meant for Visual Basic programmers who have experience with Windows and Visual Basic. Special Notes: *** During the code flush process, do not try to switch to another application. Otherwise, VB Code Flush will report an "unexpected window" error, or may even put it into an endless loop locking up the computer. (I have only run into the lock up problem once during my extensive testing, which was when I tried to switch to the hDC Alarm Clock microapp during the code flush process.) *** VB Code Flush causes Visual Basic to create a file named VBFLUSH.TMP as it performs the code flush process. This file will be created in the SET TEMP directory or in the current directory if TEMP is not found, and VB Code Flush will always delete VBFLUSH.TMP. VB Code Flush does not check available disk space before starting the code flush process, so be sure you have some free disk space. The amount of free disk space required depends on the size of the largest amount of code in a form or module, but this should not be a problem unless your disk is about to burst. If there is a problem handling the VBFLUSH.TMP file, then Visual Basic will report it and cause VB Code Flush to report an "unexpected window" error. *** If you use NoMouse (Abacus Software), then you should disable it before starting the code flush process (default toggle keystroke is ++). Otherwise, only the highlighted form or module in the Project Window will be processed, instead of all of them. This problem is due to the way NoMouse takes control of the keyboard. *** If you use VBAssist (Sheridan Software Systems), then you must make sure Visual Basic is not minimized before starting the code flush process. Otherwise, VB Code Flush will report an "unexpected window" error. This problem is due to the VBAssist window becoming the frontmost window if VB Code Flush restores Visual Basic from being minimized. VB Code Flush should work just fine as long as you observe the above information. However, I can make no guarantees with the variety of configurations and software out there. So, it is a good idea to have a backup of a project (or at least save it first in Visual Basic) before using VB Code Flush. "No warranties either expressed or implied," etc. etc. VB Code Flush is Shareware for just $4.00. Lou A. Moccia 109 Apple Lane Mt. Laurel, NJ 08054 America Online: PCC Lou (DOS Forum) Internet: pcclou@aol.com I hope you find VB Code Flush a useful utility! :)